prevent this special treatment of the $$$$ character. All other
characters are treated literally, and are used to determine the
nnnnmmmmaaaapppp _i_n_p_a_t_t_e_r_n variable values. For example, given _i_n_p_a_t_t_e_r_n
$1.$2 and the remote filename mmmmyyyyddddaaaattttaaaa....ddddaaaattttaaaa, $1 would have the
value mmmmyyyyddddaaaattttaaaa, and $2 would have the value ddddaaaattttaaaa. The _o_u_t_p_a_t_t_e_r_n
determines the resulting mapped filename. The sequences $$$$1111, $$$$2222,
...., $$$$9999 are replaced by any value resulting from the _i_n_p_a_t_t_e_r_n
template. The sequence $$$$0000 is replace by the original filename.
Additionally, the sequence [[[[_s_e_q_1,,,,_s_e_q_2]]]] is replaced by _s_e_q_1 if
_s_e_q_1 is not a null string; otherwise it is replaced by _s_e_q_2. For
example, the command nnnnmmmmaaaapppp $$$$1111....$$$$2222....$$$$3333 [[[[$$$$1111,,,,$$$$2222]]]]....[[[[$$$$2222,,,,ffffiiiilllleeee]]]] would yield
the output filename mmmmyyyyffffiiiilllleeee....ddddaaaattttaaaa for input filenames mmmmyyyyffffiiiilllleeee....ddddaaaattttaaaa
and mmmmyyyyffffiiiilllleeee....ddddaaaattttaaaa....oooolllldddd, mmmmyyyyffffiiiilllleeee....ffffiiiilllleeee for the input filename mmmmyyyyffffiiiilllleeee,
and mmmmyyyyffffiiiilllleeee....mmmmyyyyffffiiiilllleeee for the input filename ....mmmmyyyyffffiiiilllleeee. Spaces can be
included in _o_u_t_p_a_t_t_e_r_n, as in this example: